NTISthis.com

Evidence Guide: ICASAS404A - Acquire IT system components

Student: __________________________________________________

Signature: _________________________________________________

Tips for gathering evidence to demonstrate your skills

The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!

From the Wiki University

 

ICASAS404A - Acquire IT system components

What evidence can you provide to prove your understanding of each of the following citeria?

Confirm system components for acquisition

  1. Confirm client requirements, including software and operating system requirements
  2. Review technical papers and recommendations that identify required hardware and software components
  3. Review and clearly identify system components
  4. Assess and determine the fit with existing technology by consulting with system developer
  5. Identify and determine the best and current technology fit for each purpose by consulting with system developer
  6. Develop a list of required system components with specifications and possible suppliers
Confirm client requirements, including software and operating system requirements

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Review technical papers and recommendations that identify required hardware and software components

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Review and clearly identify system components

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assess and determine the fit with existing technology by consulting with system developer

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Identify and determine the best and current technology fit for each purpose by consulting with system developer

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Develop a list of required system components with specifications and possible suppliers

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Agree on methods of component acquisition

  1. 2.1 Identify and assess the client organisation's preferred acquisition methods and policies
  2. Evaluate acquisition methods and alternatives for required hardware and software components against required service levels, cost constraints, geographic constraints and user preferences
  3. Discuss and agree acquisition method with client
  4. Inform users and other stakeholders of acquisition method
2.1 Identify and assess the client organisation's preferred acquisition methods and policies

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Evaluate acquisition methods and alternatives for required hardware and software components against required service levels, cost constraints, geographic constraints and user preferences

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Discuss and agree acquisition method with client

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Inform users and other stakeholders of acquisition method

Completed
Date:

Teacher:
Evidence:

 

 

 

 

 

 

 

Assessed

Teacher: ___________________________________ Date: _________

Signature: ________________________________________________

Comments:

 

 

 

 

 

 

 

 

Instructions to Assessors

Evidence Guide

The evidence guide provides advice on assessment and must be read in conjunction with the performance criteria, required skills and knowledge, range statement and the Assessment Guidelines for the Training Package.

Overview of assessment

Critical aspects for assessment and evidence required to demonstrate competency in this unit

Evidence of the ability to:

identify correct system components

follow procurement procedures to purchase those components

fulfil technical and business requirements.

Context of and specific resources for assessment

Assessment must ensure access to:

current system architectures

current business and IT strategic plans

data models

functional process descriptions

service levels

user requirements

appropriate learning and assessment support when required

modified equipment for people with special needs.

Method of assessment

A range of assessment methods should be used to assess practical skills and knowledge. The following examples are appropriate for this unit:

verbal or written questioning to assess candidate’s knowledge of:

software and operating system requirements

organisation’s purchasing procedures

evaluation of candidate’s acquisition methods

review of candidate’s obtained quotes.

Guidance information for assessment

Holistic assessment with other units relevant to the industry sector, workplace and job role is recommended, where appropriate.

Assessment processes and techniques must be culturally appropriate, and suitable to the communication skill level, language, literacy and numeracy capacity of the candidate and the work being performed.

Indigenous people and other people from a non-English speaking background may need additional support.

In cases where practical assessment is used it should be combined with targeted questioning to assess required knowledge.

Required Skills and Knowledge

Required skills

analytical skills to:

determine software and operating system requirements

evaluate acquisition methods

communication skills to:

liaise with client users and system developer

liaise with stakeholders and service or product suppliers

negotiate with systems developers the relative merits of two or more competing devices for a purchase agreement

literacy skills to read complex technical papers

planning and organisational skills to manage project

problem-solving skills to assess the fit with existing technology and system developers.

Required knowledge

change-management systems

current industry-accepted hardware and software products

financial management options, including leasing arrangement

information-gathering techniques

risk management in relation to IT component use and items procured

quality assurance practices in relation to identifying and acquiring IT system components

client business domain

vendor product directions

organisational purchasing procedures.

Range Statement

The range statement relates to the unit of competency as a whole. It allows for different work environments and situations that may affect performance. Bold italicised wording, if used in the performance criteria, is detailed below. Essential operating conditions that may be present with training and assessment (depending on the work situation, needs of the candidate, accessibility of the item, and local industry and regional contexts) may also be included.

Client may include:

external organisations

individuals

internal departments

internal employees.

Requirements may relate to:

business

database

network

people in the organisation

platform

system.

Software may include:

commercial applications

customised

in-house

organisation-specific

packaged.

Operating system may include:

Linux

Mac

Windows.

Hardware may include:

CD and DVD drives

central processing unit (CPU) and CPU upgrades

complementary metal oxide semiconductor (CMOS) battery

fax or modem cards

interface cards

internal and external storage devices

modems and other connectivity devices, such as asymmetric digital subscriber line (ADSL) modems

motherboards

networks

personal computers

random access memory (RAM) upgrades

remote sites

servers

workstations.

System components may include:

facilities management

hardware, such as internal expansion devices and external peripheral devices

integration and implementation services

personal computers, networks and printers

software, such as applications, utilities and operating systems.

Specifications may include:

current system functionality

technical requirements

user problem statement.

Acquisition methods may include:

lease

new or refurbished

outsourced

purchase

rental.